Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

The adapter-core normalizeWritebackStatus is behaviorally equivalent to the removed local fallback for the paths the runtime relies on:

• No receipt → state: 'no_receipt' (matches old fallback). The runtime's fire-and-forget guard (writebackTimeoutMs === 0 && state === 'no_receipt') still works, and the error path for other no_receipt cases still throws. Confirmed by the passing tests.
• Receipt present → state: 'succeeded' with id derived identically (receipt.id ?? receipt.created). Matches old fallback.

The behavior is preserved. No fail-closed→fail-open regression. The runtime's writeJsonFile logic (the safety-critical guard) is unchanged by this PR — only the source of normalizeWritebackStatus/WritebackError moved from a local fallback to the upstream package.

This PR is a clean dependency-consolidation change with full CI green. I found no issues requiring edits. There are no bot or reviewer comments to address. No mechanical fixes needed.

Review Summary

PR #245 (cloud #2297): chore(runtime): consume adapter-core writeback normalizer

The PR bumps @relayfile/adapter-core from ^0.3.59 to ^0.3.60 in persona-kit and runtime, updates pnpm-lock.yaml accordingly, and deletes the ~100-line local fallback implementation in packages/runtime/src/clients/index.ts (the FallbackWritebackError class, the AdapterVfsClientExtensions shim, and the local NormalizedWritebackState/NormalizedWritebackStatus types + normalizeWritebackStatus). These are now imported directly from @relayfile/adapter-core/vfs-client, which provides them natively in 0.3.60.

Verification (ran the full CI sequence end-to-end):

• pnpm install --frozen-lockfile — clean, "Lockfile is up to date" (lockfile changes are consistent)
• pnpm -r run build — all 15 packages built, including runtime and persona-kit
• pnpm run lint — pass
• pnpm run typecheck — pass (confirms all 17 imported symbols, including the 4 moved ones, resolve against 0.3.60)
• pnpm run test — all packages pass, 0 failures, including the three writeback tests in packages/runtime/src/clients/index.test.ts

Behavioral / safety checks:

• Confirmed adapter-core 0.3.60 exports normalizeWritebackStatus, WritebackError, NormalizedWritebackState, NormalizedWritebackStatus (and the rest).
• Confirmed adapter-core's WritebackError extends RelayfileWritebackError, so the instanceof WorkforceIntegrationError assertion in index.test.ts:53 still holds (both resolve to the same installed adapter-core class — no dual-package hazard).
• Compared adapter-core's normalizeWritebackStatus against the removed local fallback: equivalent for the states the runtime depends on — no_receipt when receipt absent, succeeded (with id = receipt.id ?? receipt.created) when present.
• The safety-critical guard in writeJsonFile (writebackTimeoutMs === 0 && normalized.state === 'no_receipt' → return without throwing; otherwise throw) is unchanged by this PR. No fail-closed→fail-open regression.

Files edited: none. No mechanical/lint fixes were required; the working tree is left unchanged.

Addressed comments

• No bot or reviewer comments were present. .workforce/ contains only pr.diff, changed-files.txt, and context.json (no comments/threads), and context.json carries no review metadata. Nothing to address.

Advisory Notes

• None. The change is self-contained and within the PR's stated purpose (consuming the adapter-core writeback normalizer).

The PR is a clean dependency consolidation, fully green across build/lint/typecheck/test with no behavioral changes. The remaining merge decision is human judgment.